FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource Requirements/FHIR Server from package hl7.ehrs.ehrsfmr21#current (16 ms)

Package hl7.ehrs.ehrsfmr21
Type Requirements
Id Id
FHIR Version R5
Source http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-TI.1.4.html
Url http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.1.4
Version 2.1.0
Status active
Date 2024-11-26T16:30:50+00:00
Name TI_1_4_Patient_Access_Management
Title TI.1.4 Patient Access Management (Function)
Experimental False
Realm uv
Authority hl7
Description Manage a patient's access to personal health information.
Purpose A healthcare delivery organization will be able to manage a patient's ability to view his or her EHR based on organization policy or jurisdictional law. Typically, a patient or their legal representative (e.g., guardian, surrogate) has the right to view his or her EHR.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found



Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Manage a patient's access to personal health information.

Description I:

A healthcare delivery organization will be able to manage a patient's ability to view his or her EHR based on organization policy or jurisdictional law. Typically, a patient or their legal representative (e.g., guardian, surrogate) has the right to view his or her EHR.

Criteria N:
TI.1.4#01 dependent conditional SHALL

IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.3]] (Entity Access Control).

TI.1.4#02 dependent conditional SHALL

IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.2]] (Entity Authorization).


Source

{
  "resourceType" : "Requirements",
  "id" : "EHRSFMR2.1-TI.1.4",
  "meta" : {
    "profile" : [
      "http://hl7.org/ehrs/StructureDefinition/FMFunction"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage a patient's access to personal health information.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>A healthcare delivery organization will be able to manage a patient's ability to view his or her EHR based on organization policy or jurisdictional law. Typically, a patient or their legal representative (e.g., guardian, surrogate) has the right to view his or her EHR.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.1.4#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.3]] (Entity Access Control).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.1.4#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n <i>conditional</i>\n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.2]] (Entity Authorization).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
  },
  "url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.1.4",
  "version" : "2.1.0",
  "name" : "TI_1_4_Patient_Access_Management",
  "title" : "TI.1.4 Patient Access Management (Function)",
  "status" : "active",
  "date" : "2024-11-26T16:30:50+00:00",
  "publisher" : "EHR WG",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description" : "Manage a patient's access to personal health information.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "purpose" : "A healthcare delivery organization will be able to manage a patient's ability to view his or her EHR based on organization policy or jurisdictional law. Typically, a patient or their legal representative (e.g., guardian, surrogate) has the right to view his or her EHR.",
  "statement" : [
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-TI.1.4-01",
      "label" : "TI.1.4#01",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : true,
      "requirement" : "IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.3]] (Entity Access Control).",
      "derivedFrom" : "EHR-S_FM_R1.1 IN.1.4#1"
    },
    {
      "extension" : [
        {
          "url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
          "valueBoolean" : true
        }
      ],
      "key" : "EHRSFMR2.1-TI.1.4-02",
      "label" : "TI.1.4#02",
      "conformance" : [
        "SHALL"
      ],
      "conditionality" : true,
      "requirement" : "IF organizational policy allows patient access to the EHR-S, THEN the system SHALL conform to function [[TI.1.2]] (Entity Authorization)."
    }
  ]
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.